Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: APP-255 add supported file types link #2466

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

blushi
Copy link
Member

@blushi blushi commented Sep 9, 2024

Description

https://regennetwork.atlassian.net/browse/APP-255

Also fixes some small translation issue


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • provided a link to the relevant issue or specification
  • provided instructions on how to test
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

How to test

From https://deploy-preview-2466--regen-marketplace.netlify.app/, log in and create a post. From the post form, check that clicking "View all supported file types»" opens the right link in a new tab.

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items
.

I have...

  • confirmed all author checklist items have been addressed
  • reviewed code correctness and readability
  • verified React components follow DRY principles
  • reviewed documentation is accurate
  • reviewed tests
  • manually tested (if applicable)

Copy link

netlify bot commented Sep 9, 2024

Deploy Preview for regen-website ready!

Name Link
🔨 Latest commit bc2f7b4
🔍 Latest deploy log https://app.netlify.com/sites/regen-website/deploys/66e147e2673cea00088f91a9
😎 Deploy Preview https://deploy-preview-2466--regen-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@blushi blushi requested a review from r41ph September 9, 2024 11:02
@blushi
Copy link
Member Author

blushi commented Sep 9, 2024

@erikalogie see testing instructions

</Trans>
<Link href="#">
&nbsp;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it'd be better to use padding instead of &nbsp;

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? Using a white-space means it will adjust based on the font size so we would need to provide two padding values for mobile/desktop to get the same result.
I thought this made sense since the two elements are displayed inline, just like one single sentence but maybe there are other reasons I'm not aware of?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As &nbsp; adjusts with font size we can end up losing control over the space between the elements if for example the browser settings override our font sizes. Also, using CSS for spacing keeps content and style separate, which is a good practice. I think using margin or padding is a more reliable way to control spacing between inline elements and it's easier to update and maintain if the design changes.

Copy link
Member Author

@blushi blushi Sep 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree but I believe in this particular case, it's rather a matter of content than spacing. We really want this to feel like it should be just a paragraph of text. Just like we do for links within post comment for instance.

image

@blushi blushi requested a review from r41ph September 10, 2024 15:53
</Trans>
<Link href="#">
&nbsp;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As &nbsp; adjusts with font size we can end up losing control over the space between the elements if for example the browser settings override our font sizes. Also, using CSS for spacing keeps content and style separate, which is a good practice. I think using margin or padding is a more reliable way to control spacing between inline elements and it's easier to update and maintain if the design changes.

@erikalogie
Copy link
Collaborator

LGTM

@blushi blushi force-pushed the chore-APP-255-supported-files-link branch from 05d58d0 to bc2f7b4 Compare September 11, 2024 07:33
@blushi blushi enabled auto-merge (squash) September 11, 2024 07:34
@blushi blushi merged commit 0cd4dc8 into dev Sep 11, 2024
2 checks passed
@blushi blushi deleted the chore-APP-255-supported-files-link branch September 11, 2024 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants